-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement MaxCumulativeFailsafeSeconds #19582
Merged
tehampson
merged 9 commits into
project-chip:master
from
tehampson:max-cumulative-failsafe-seconds-issue-19331
Jun 15, 2022
Merged
Implement MaxCumulativeFailsafeSeconds #19582
tehampson
merged 9 commits into
project-chip:master
from
tehampson:max-cumulative-failsafe-seconds-issue-19331
Jun 15, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pullapprove
bot
requested review from
andy31415,
anush-apple,
arkq,
Byungjoo-Lee,
bzbarsky-apple,
carol-apple,
chrisdecenzo,
chshu and
chulspro
June 14, 2022 18:47
pullapprove
bot
requested review from
woody-apple,
xylophone21 and
yunhanw-google
June 14, 2022 18:47
andy31415
reviewed
Jun 14, 2022
andy31415
reviewed
Jun 14, 2022
andy31415
approved these changes
Jun 14, 2022
PR #19582: Size comparison from 4b6fc80 to 2906425 Increases (28 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, mbed, nrfconnect, p6, telink)
Decreases (5 builds for cc13x2_26x2)
Full report (28 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, mbed, nrfconnect, p6, telink)
|
PR #19582: Size comparison from 4b6fc80 to 5f26379 Increases (28 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, mbed, nrfconnect, p6, telink)
Decreases (5 builds for cc13x2_26x2)
Full report (28 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, mbed, nrfconnect, p6, telink)
|
bzbarsky-apple
approved these changes
Jun 15, 2022
src/app/zap-templates/zcl/data-model/chip/general-commissioning-cluster.xml
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Change overview
Testing
How was this tested? (at least one bullet point required)
CHIP_DEVICE_CONFIG_MAX_CUMULATIVE_FAILSAFE_SEC 10
andCHIP_DEVICE_CONFIG_FAILSAFE_EXPIRY_LENGTH_SEC 1
../chip-tool generalcommissioning arm-fail-safe 20 1 1 0
to confirm that max cumulative timer expired first triggering cleanup./chip-tool generalcommissioning arm-fail-safe 9 1 1 0
, then again after 6 seconds to confirm that max cumulative timer expired first triggering cleanup